NTISthis.com

Evidence Guide: ICTSAS426 - Locate and troubleshoot ICT equipment, system and software faults

Student: __________________________________________________

Signature: _________________________________________________

Tips for gathering evidence to demonstrate your skills

The important thing to remember when gathering evidence is that the more evidence the better - that is, the more evidence you gather to demonstrate your skills, the more confident an assessor can be that you have learned the skills not just at one point in time, but are continuing to apply and develop those skills (as opposed to just learning for the test!). Furthermore, one piece of evidence that you collect will not usualy demonstrate all the required criteria for a unit of competency, whereas multiple overlapping pieces of evidence will usually do the trick!

From the Wiki University

 

ICTSAS426 - Locate and troubleshoot ICT equipment, system and software faults

What evidence can you provide to prove your understanding of each of the following citeria?

Choose the most appropriate fault finding method

  1. Develop a troubleshooting process to help resolve problems
  2. Analyse and document the system that requires troubleshooting
  3. Identify available fault finding tools and determine the most appropriate for the identified problem
  4. Obtain the required fault finding tools
  5. Identify legislation, health and safety requirements, codes, regulations and standards related to the problem area
Develop a troubleshooting process to help resolve problems

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Analyse and document the system that requires troubleshooting

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Identify available fault finding tools and determine the most appropriate for the identified problem

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Obtain the required fault finding tools

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Identify legislation, health and safety requirements, codes, regulations and standards related to the problem area

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Analyse the problem to be solved

  1. Collect data relevant to the system
  2. Analyse the data to determine if there is a problem and the nature of the problem
  3. Determine specific symptoms of hardware, operating system and printer problems
Collect data relevant to the system

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Analyse the data to determine if there is a problem and the nature of the problem

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Determine specific symptoms of hardware, operating system and printer problems

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Identify a solution and rectify the problem

  1. Formulate a solution and make provision for rollback
  2. Systematically test variables until the problem is isolated
  3. Rectify the problem
  4. Create a list of probable causes of the problem
Formulate a solution and make provision for rollback

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Systematically test variables until the problem is isolated

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Rectify the problem

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Create a list of probable causes of the problem

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Test system and complete documentation

  1. Test the system to ensure the problem has been solved and record results
  2. Identify and implement common preventative maintenance techniques to support ongoing maintenance strategies
  3. Document the signs and symptoms of the problem and its solution, and load to database of problems or solutions for future reference
Test the system to ensure the problem has been solved and record results

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Identify and implement common preventative maintenance techniques to support ongoing maintenance strategies

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Document the signs and symptoms of the problem and its solution, and load to database of problems or solutions for future reference

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Assessed

Teacher: ___________________________________ Date: _________

Signature: ________________________________________________

Comments:

 

 

 

 

 

 

 

 

Instructions to Assessors

Evidence Guide

ELEMENT

PERFORMANCE CRITERIA

Elements describe the essential outcomes.

Performance criteria describe the performance needed to demonstrate achievement of the element.

1. Choose the most appropriate fault finding method

1.1 Develop a troubleshooting process to help resolve problems

1.2 Analyse and document the system that requires troubleshooting

1.3 Identify available fault finding tools and determine the most appropriate for the identified problem

1.4 Obtain the required fault finding tools

1.5 Identify legislation, health and safety requirements, codes, regulations and standards related to the problem area

2. Analyse the problem to be solved

2.1 Collect data relevant to the system

2.2 Analyse the data to determine if there is a problem and the nature of the problem

2.3 Determine specific symptoms of hardware, operating system and printer problems

3. Identify a solution and rectify the problem

3.1 Formulate a solution and make provision for rollback

3.2 Systematically test variables until the problem is isolated

3.3 Rectify the problem

3.4 Create a list of probable causes of the problem

4. Test system and complete documentation

4.1 Test the system to ensure the problem has been solved and record results

4.2 Identify and implement common preventative maintenance techniques to support ongoing maintenance strategies

4.3 Document the signs and symptoms of the problem and its solution, and load to database of problems or solutions for future reference

Required Skills and Knowledge

ELEMENT

PERFORMANCE CRITERIA

Elements describe the essential outcomes.

Performance criteria describe the performance needed to demonstrate achievement of the element.

1. Choose the most appropriate fault finding method

1.1 Develop a troubleshooting process to help resolve problems

1.2 Analyse and document the system that requires troubleshooting

1.3 Identify available fault finding tools and determine the most appropriate for the identified problem

1.4 Obtain the required fault finding tools

1.5 Identify legislation, health and safety requirements, codes, regulations and standards related to the problem area

2. Analyse the problem to be solved

2.1 Collect data relevant to the system

2.2 Analyse the data to determine if there is a problem and the nature of the problem

2.3 Determine specific symptoms of hardware, operating system and printer problems

3. Identify a solution and rectify the problem

3.1 Formulate a solution and make provision for rollback

3.2 Systematically test variables until the problem is isolated

3.3 Rectify the problem

3.4 Create a list of probable causes of the problem

4. Test system and complete documentation

4.1 Test the system to ensure the problem has been solved and record results

4.2 Identify and implement common preventative maintenance techniques to support ongoing maintenance strategies

4.3 Document the signs and symptoms of the problem and its solution, and load to database of problems or solutions for future reference

Evidence of the ability to:

determine the most appropriate fault finding method

document the troubleshooting process

analyse and identify faults

obtain suitable tools and equipment

apply simple checks, tests and fault finding methodologies

apply the recommended means to rectify fault and document results.

Note: Evidence must be provided for at least TWO organisations or situations.

To complete the unit requirements safely and effectively, the individual must:

explain client support and maintenance practices

identify and describe current industry accepted hardware and software products, including features and capabilities

discuss the system's current functionality, including details of the proposed system modifications

describe one or more change management tools

explain the key features of quality assurance practices with regard to locating and troubleshooting information and communications technology (ICT) equipment, system and software faults

outline the change control procedures of the organisation

describe a range of trouble shooting methodologies and system testing tools

list and describe common symptoms of faulty ICT equipment

identify and describe legislative, regulatory, standards or codes of practice that impact on the ICT service sector.